fix(RSC): Always read header in RSC render #506
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
At this moment I get a new error that I don't know if it has to do with nextjs 13.5.4 or with next-intl. The thing is that in all the tutorials that I have seen and even documentation, everywhere in the rootlayout they use the useLocale() hook and no one has a problem, it does give me a problem since it is a hook and the hooks cannot be server side ✓ Compiled in 761ms (1242 modules)
⨯ node_modules/next-intl/dist/esm/server/RequestLocale.js (1:580) @ eval
⨯ Error: Unable to find `next-intl` locale, have you configured the middleware?`
at RootLayout (./src/app/[locale]/layout.tsx:29:73)
at async Promise.all (index 0)
null
My configuration is to the letter with the documentation and on par with other programmers, but no one else gets the same error as me, or at least for the same reason. |
|
I get the same error as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should fix #446
As far as I understand the issue currently, something like this happens:
NEXT_LOCALEcookie is setNEXT_LOCALEcookie is suddenly not availableIf this is the case, this would fix the issue.
If however the middlware doesn't run at all for some reason, this will not make a difference. However, since this doesn't seem to have any downsides (possible since newer Next.js versions), this might simplify the code anyway and is a welcome change.